Vcenter Namespaces ResourceQuotaOptionsV1Update
The Vcenter Namespaces ResourceQuotaOptionsV1Update schema represents the changes to resource quota limits which are set on the namespace. Refer to <\a> Kubernetes Resource Quota for information related to the properties of this object and what they map to.
This schema was added in vSphere API 7.0.0.0.
{
"memory_limit": 0,
"memory_limit_unset": false,
"memory_limit_default": 0,
"memory_limit_default_unset": false,
"memory_request_default": 0,
"memory_request_default_unset": false,
"cpu_limit": 0,
"cpu_limit_unset": false,
"cpu_limit_default": 0,
"cpu_limit_default_unset": false,
"cpu_request_default": 0,
"cpu_request_default_unset": false,
"storage_request_limit": 0,
"storage_request_limit_unset": false,
"pod_count": 0,
"pod_count_unset": false,
"service_count": 0,
"service_count_unset": false,
"deployment_count": 0,
"deployment_count_unset": false,
"daemon_set_count": 0,
"daemon_set_count_unset": false,
"replica_set_count": 0,
"replica_set_count_unset": false,
"replication_controller_count": 0,
"replication_controller_count_unset": false,
"stateful_set_count": 0,
"stateful_set_count_unset": false,
"config_map_count": 0,
"config_map_count_unset": false,
"secret_count": 0,
"secret_count_unset": false,
"persistent_volume_claim_count": 0,
"persistent_volume_claim_count_unset": false,
"job_count": 0,
"job_count_unset": false
}This represents the new value for 'limits.memory' option which is equivalent to the maximum memory limit (in mebibytes) across all pods in the namespace. This field is ignored if Vcenter Namespaces ResourceQuotaOptionsV1Update.memory_limit_unset is set to true.
This property was added in vSphere API 7.0.0.0.
If missing or null, the existing memory limit on the ResourcePool will be unchanged if Vcenter Namespaces ResourceQuotaOptionsV1Update.memory_limit_unset is missing or null or set to false.
This represents the intent of the change to Vcenter Namespaces ResourceQuotaOptionsV1Update.memory_limit. If this field is set to true, the existing memory limit on the ResourcePool is removed. If this field is set to false, the existing memory limit will be changed to the value specified in Vcenter Namespaces ResourceQuotaOptionsV1Update.memory_limit, if any.
This property was added in vSphere API 7.0.0.0.
If missing or null, the existing memory limit will be changed to the value specified in Vcenter Namespaces ResourceQuotaOptionsV1Update.memory_limit, if any.
This represents the new value for the default memory limit (in mebibytes) for containers in the pod. This field is ignored if Vcenter Namespaces ResourceQuotaOptionsV1Update.memory_limit_default_unset is set to true.
This property was added in vSphere API 7.0.0.0.
If missing or null, the existing memory limit will be unchanged if Vcenter Namespaces ResourceQuotaOptionsV1Update.memory_limit_default_unset is missing or null or set to false.
This represents the intent of the change to Vcenter Namespaces ResourceQuotaOptionsV1Update.memory_limit_default. If this field is set to true, the existing default memory limit on containers in the pod is removed. If this field is set to false, the existing default memory limit will be changed to the value specified in Vcenter Namespaces ResourceQuotaOptionsV1Update.memory_limit_default, if any.
This property was added in vSphere API 7.0.0.0.
If missing or null, the existing default memory limit will be changed to the value specified in Vcenter Namespaces ResourceQuotaOptionsV1Update.memory_limit_default, if any.
This represents the new value for the default memory request (in mebibytes) for containers in the pod. This field is ignored if Vcenter Namespaces ResourceQuotaOptionsV1Update.memory_request_default_unset is set to true.
This property was added in vSphere API 7.0.0.0.
If missing or null, the existing memory request will be unchanged if Vcenter Namespaces ResourceQuotaOptionsV1Update.memory_request_default_unset is missing or null or set to false.
This represents the intent of the change to Vcenter Namespaces ResourceQuotaOptionsV1Update.memory_request_default. If this field is set to true, the existing default memory request on containers in the pod will be removed. If this field is set to false, the existing default memory request will be changed to the value specified in Vcenter Namespaces ResourceQuotaOptionsV1Update.memory_request_default, if any.
This property was added in vSphere API 7.0.0.0.
If missing or null, the existing default memory request will be changed to the value specified in Vcenter Namespaces ResourceQuotaOptionsV1Update.memory_request_default, if any.
This represents the new value for 'limits.cpu' option which is equivalent to the maximum CPU limit (in MHz) across all pods in the namespace. This field is ignored if Vcenter Namespaces ResourceQuotaOptionsV1Update.cpu_limit_unset is set to true. If specified, this limit should be at least 10 MHz.
This property was added in vSphere API 7.0.0.0.
If missing or null, the existing CPU limit on the ResourcePool will be unchanged if Vcenter Namespaces ResourceQuotaOptionsV1Update.cpu_limit_unset is missing or null or set to false.
This represents the intent of the change to Vcenter Namespaces ResourceQuotaOptionsV1Update.cpu_limit. If this field is set to true, the existing CPU limit on the ResourcePool is removed. If this field is set to false, the existing CPU limit will be changed to the value specified in Vcenter Namespaces ResourceQuotaOptionsV1Update.cpu_limit, if any.
This property was added in vSphere API 7.0.0.0.
If missing or null, the existing CPU limit will be changed to the value specified in Vcenter Namespaces ResourceQuotaOptionsV1Update.memory_limit, if any.
This represents the new value for the default CPU limit (in Mhz) for containers in the pod. This field is ignored if Vcenter Namespaces ResourceQuotaOptionsV1Update.cpu_limit_default_unset is set to true. If specified, this limit should be at least 10 MHz.
This property was added in vSphere API 7.0.0.0.
If missing or null, the existing default CPU limit will be unchanged if Vcenter Namespaces ResourceQuotaOptionsV1Update.cpu_limit_default_unset is missing or null or set to false.
This represents the intent of the change to Vcenter Namespaces ResourceQuotaOptionsV1Update.cpu_limit_default. If this field is set to true, the existing default CPU limit on containers in the pod is removed. If this field is set to false, the existing default CPU limit will be changed to the value specified in Vcenter Namespaces ResourceQuotaOptionsV1Update.cpu_limit_default, if any.
This property was added in vSphere API 7.0.0.0.
If missing or null, the existing default CPU limit will be changed to the value specified in Vcenter Namespaces ResourceQuotaOptionsV1Update.cpu_limit_default, if any.
This represents the new value for the default CPU request (in Mhz) for containers in the pod. This field is ignored if Vcenter Namespaces ResourceQuotaOptionsV1Update.cpu_request_default_unset is set to true. If specified, this field should be at least 10 MHz.
This property was added in vSphere API 7.0.0.0.
If missing or null, the existing default CPU request will be unchanged if Vcenter Namespaces ResourceQuotaOptionsV1Update.cpu_request_default_unset is missing or null or set to false.
This represents the intent of the change to Vcenter Namespaces ResourceQuotaOptionsV1Update.cpu_request_default. If this field is set to true, the existing default CPU request on containers in the pod is removed. If this field is set to false, the existing default CPU request will be changed to the value specified in Vcenter Namespaces ResourceQuotaOptionsV1Update.cpu_request_default, if any.
This property was added in vSphere API 7.0.0.0.
If missing or null, the existing default CPU request will be changed to the value specified in Vcenter Namespaces ResourceQuotaOptionsV1Update.cpu_request_default, if any.
This represents the new value for 'requests.storage' which is the limit on storage requests (in mebibytes) across all persistent volume claims from pods in the namespace. This field is ignored if if Vcenter Namespaces ResourceQuotaOptionsV1Update.storage_request_limit_unset is set to true.
This property was added in vSphere API 7.0.0.0.
If missing or null, the existing storage request limit will be unchanged if Vcenter Namespaces ResourceQuotaOptionsV1Update.storage_request_limit_unset is missing or null or set to false. the namespace.
This represents the intent of the change to Vcenter Namespaces ResourceQuotaOptionsV1Update.storage_request_limit. If this field is set to true, the existing storage request limit will be reset. If this field is set to false, the existing storage request limit will be changed to the value specified in Vcenter Namespaces ResourceQuotaOptionsV1Update.storage_request_limit, if any.
This property was added in vSphere API 7.0.0.0.
If missing or null, the existing storage request limit will be changed to the value specified in Vcenter Namespaces ResourceQuotaOptionsV1Update.storage_request_limit, if any.
This represents the new value for 'podCount' option which is the maximum number of pods in the namespace. This field is ignored if Vcenter Namespaces ResourceQuotaOptionsV1Update.pod_count_unset is set to true.
This property was added in vSphere API 7.0.0.0.
If missing or null, the existing 'podCount' limit will be unchanged if Vcenter Namespaces ResourceQuotaOptionsV1Update.pod_count_unset is missing or null or set to false.
This represents the intent of the change to Vcenter Namespaces ResourceQuotaOptionsV1Update.pod_count. If this field is set to true, the existing 'podCount' limit on the namespace will be reset. If this field is set to false, the existing CPU limit will be changed to the value specified in Vcenter Namespaces ResourceQuotaOptionsV1Update.pod_count, if any.
This property was added in vSphere API 7.0.0.0.
If missing or null, the existing 'podCount' limit will be changed to the value specified in Vcenter Namespaces ResourceQuotaOptionsV1Update.pod_count, if any.
This represents the new value for 'serviceCount' option which is the maximum number of services in the namespace. This field is ignored if Vcenter Namespaces ResourceQuotaOptionsV1Update.service_count_unset is set to true.
This property was added in vSphere API 7.0.0.0.
If missing or null, the existing 'serviceCount' limit will be unchanged if Vcenter Namespaces ResourceQuotaOptionsV1Update.service_count_unset is missing or null or set to false.
This represents the intent of the change to Vcenter Namespaces ResourceQuotaOptionsV1Update.service_count. If this field is set to true, the existing 'serviceCount' limit on the namespace will be reset. If this field is set to false, the existing service count limit will be changed to the value specified in Vcenter Namespaces ResourceQuotaOptionsV1Update.service_count, if any.
This property was added in vSphere API 7.0.0.0.
If missing or null, the existing 'serviceCount' limit will be changed to the value specified in Vcenter Namespaces ResourceQuotaOptionsV1Update.service_count, if any.
This represents the new value for 'deploymentCount' option which is the maximum number of deployments in the namespace. This field is ignored if Vcenter Namespaces ResourceQuotaOptionsV1Update.deployment_count_unset is set to true.
This property was added in vSphere API 7.0.0.0.
If missing or null, the existing 'deploymentCount' limit will be unchanged if Vcenter Namespaces ResourceQuotaOptionsV1Update.deployment_count_unset is missing or null or set to false.
This represents the intent of the change to Vcenter Namespaces ResourceQuotaOptionsV1Update.deployment_count. If this field is set to true, the existing 'deploymentCount' limit on the namespace will be reset. If this field is set to false, the existing deployment count limit will be changed to the value specified in Vcenter Namespaces ResourceQuotaOptionsV1Update.deployment_count, if any.
This property was added in vSphere API 7.0.0.0.
If missing or null, the existing 'deploymentCount' limit will be changed to the value specified in Vcenter Namespaces ResourceQuotaOptionsV1Update.deployment_count, if any.
This represents the new value for 'daemonSetCount' option which is the maximum number of DaemonSets in the namespace. This field is ignored if Vcenter Namespaces ResourceQuotaOptionsV1Update.daemon_set_count_unset is set to true.
This property was added in vSphere API 7.0.0.0.
If missing or null, the existing 'daemonSetCount' limit will be unchanged if Vcenter Namespaces ResourceQuotaOptionsV1Update.daemon_set_count_unset is missing or null or set to false.
This represents the intent of the change to Vcenter Namespaces ResourceQuotaOptionsV1Update.daemon_set_count. If this field is set to true, the existing 'daemonSetCount' limit on the namespace will be reset. If this field is set to false, the existing daemonset count limit will be changed to the value specified in Vcenter Namespaces ResourceQuotaOptionsV1Update.daemon_set_count, if any.
This property was added in vSphere API 7.0.0.0.
If missing or null, the existing 'daemonSetCount' limit will be changed to the value specified in Vcenter Namespaces ResourceQuotaOptionsV1Update.daemon_set_count, if any.
This represents the new value for 'replicaSetCount' option which is the maximum number of ReplicaSets in the namespace. This field is ignored if Vcenter Namespaces ResourceQuotaOptionsV1Update.replica_set_count_unset is set to true.
This property was added in vSphere API 7.0.0.0.
If missing or null, the existing 'replicaSetCount' limit will be unchanged if Vcenter Namespaces ResourceQuotaOptionsV1Update.replica_set_count_unset is missing or null or set to false.
This represents the intent of the change to Vcenter Namespaces ResourceQuotaOptionsV1Update.replica_set_count. If this field is set to true, the existing 'replicaSetCount' limit on the namespace will be reset. If this field is set to false, the existing replicaset count limit will be changed to the value specified in Vcenter Namespaces ResourceQuotaOptionsV1Update.replica_set_count, if any.
This property was added in vSphere API 7.0.0.0.
If missing or null, the existing 'replicaSetCount' limit will be changed to the value specified in Vcenter Namespaces ResourceQuotaOptionsV1Update.replica_set_count, if any.
This represents the new value for 'replicationControllerCount' option which is the maximum number of ReplicationControllers in the namespace. This field is ignored if Vcenter Namespaces ResourceQuotaOptionsV1Update.replication_controller_count_unset is set to true.
This property was added in vSphere API 7.0.0.0.
If missing or null, the existing 'replicationControllerCount' limit will be unchanged if Vcenter Namespaces ResourceQuotaOptionsV1Update.replication_controller_count_unset is missing or null or set to false.
This represents the intent of the change to Vcenter Namespaces ResourceQuotaOptionsV1Update.replication_controller_count. If this field is set to true, the existing 'replicationControllerCount' limit on the namespace will be reset. If this field is set to false, the existing replicationcontroller count limit will be changed to the value specified in Vcenter Namespaces ResourceQuotaOptionsV1Update.replication_controller_count, if any.
This property was added in vSphere API 7.0.0.0.
If missing or null, the existing 'replicationControllerCount' limit will be changed to the value specified in Vcenter Namespaces ResourceQuotaOptionsV1Update.replication_controller_count, if any.
This represents the new value for 'statefulSetCount' option which is the maximum number of StatefulSets in the namespace. This field is ignored if Vcenter Namespaces ResourceQuotaOptionsV1Update.stateful_set_count_unset is set to true.
This property was added in vSphere API 7.0.0.0.
If missing or null, the existing 'statefulSetCount' limit will be unchanged if Vcenter Namespaces ResourceQuotaOptionsV1Update.stateful_set_count_unset is missing or null or set to false.
This represents the intent of the change to Vcenter Namespaces ResourceQuotaOptionsV1Update.stateful_set_count. If this field is set to true, the existing 'statefulSetCount' limit on the namespace will be reset. If this field is set to false, the existing statefulset count limit will be changed to the value specified in Vcenter Namespaces ResourceQuotaOptionsV1Update.stateful_set_count, if any.
This property was added in vSphere API 7.0.0.0.
If missing or null, the existing 'statefulSetCount' limit will be changed to the value specified in Vcenter Namespaces ResourceQuotaOptionsV1Update.stateful_set_count, if any.
This represents the new value for 'configMapCount' option which is the maximum number of ConfigMaps in the namespace. This field is ignored if Vcenter Namespaces ResourceQuotaOptionsV1Update.config_map_count_unset is set to true.
This property was added in vSphere API 7.0.0.0.
If missing or null, the existing 'configMapCount' limit will be unchanged if Vcenter Namespaces ResourceQuotaOptionsV1Update.config_map_count_unset is missing or null or set to false.
This represents the intent of the change to Vcenter Namespaces ResourceQuotaOptionsV1Update.config_map_count. If this field is set to true, the existing 'configMapCount' limit on the namespace will be reset. If this field is set to false, the existing configmap count limit will be changed to the value specified in Vcenter Namespaces ResourceQuotaOptionsV1Update.config_map_count, if any.
This property was added in vSphere API 7.0.0.0.
If missing or null, the existing 'configMapCount' limit will be changed to the value specified in Vcenter Namespaces ResourceQuotaOptionsV1Update.config_map_count, if any.
This represents the new value for 'secretCount' option which is the maximum number of secrets in the namespace. This field is ignored if Vcenter Namespaces ResourceQuotaOptionsV1Update.secret_count_unset is set to true.
This property was added in vSphere API 7.0.0.0.
If missing or null, the existing 'secretCount' limit will be unchanged if Vcenter Namespaces ResourceQuotaOptionsV1Update.secret_count_unset is missing or null or set to false.
This represents the intent of the change to Vcenter Namespaces ResourceQuotaOptionsV1Update.secret_count. If this field is set to true, the existing 'secretCount' limit on the namespace will be reset. If this field is set to false, the existing secret count limit will be changed to the value specified in Vcenter Namespaces ResourceQuotaOptionsV1Update.secret_count, if any.
This property was added in vSphere API 7.0.0.0.
If missing or null, the existing 'secretCount' limit will be changed to the value specified in Vcenter Namespaces ResourceQuotaOptionsV1Update.secret_count, if any.
This represents the new value for 'persistentVolumeClaimCount' option which is the maximum number of PersistentVolumeClaims in the namespace. This field is ignored if Vcenter Namespaces ResourceQuotaOptionsV1Update.persistent_volume_claim_count_unset is set to true.
This property was added in vSphere API 7.0.0.0.
If missing or null, the existing 'persistentVolumeClaimCount' limit will be unchanged if Vcenter Namespaces ResourceQuotaOptionsV1Update.persistent_volume_claim_count_unset is missing or null or set to false.
This represents the intent of the change to Vcenter Namespaces ResourceQuotaOptionsV1Update.persistent_volume_claim_count. If this field is set to true, the existing 'persistentVolumeClaimCount' limit on the namespace will be reset. If this field is set to false, the existing replicationcontroller count limit will be changed to the value specified in Vcenter Namespaces ResourceQuotaOptionsV1Update.persistent_volume_claim_count, if any.
This property was added in vSphere API 7.0.0.0.
If missing or null, the existing 'persistentVolumeClaimCount' limit will be changed to the value specified in Vcenter Namespaces ResourceQuotaOptionsV1Update.persistent_volume_claim_count, if any.
This represents the new value for 'jobCount' option which is the maximum number of jobs in the namespace. This field is ignored if Vcenter Namespaces ResourceQuotaOptionsV1Update.job_count_unset is set to true.
This property was added in vSphere API 7.0.0.0.
If missing or null, the existing 'jobCount' limit will be unchanged if Vcenter Namespaces ResourceQuotaOptionsV1Update.job_count_unset is missing or null or set to false.
This represents the intent of the change to Vcenter Namespaces ResourceQuotaOptionsV1Update.job_count. If this field is set to true, the existing 'jobCount' limit on the namespace will be reset. If this field is set to false, the existing secret count limit will be changed to the value specified in Vcenter Namespaces ResourceQuotaOptionsV1Update.job_count, if any.
This property was added in vSphere API 7.0.0.0.
If missing or null, the existing 'jobCount' limit will be changed to the value specified in Vcenter Namespaces ResourceQuotaOptionsV1Update.job_count, if any.